Ham Radio 2000 #1/Ham Radio 2000.iso/ham2000/packet/p_aa4re/bbrequ2a/reqtip.dat

Text File | 1992-05-22 | 35.4 KB | 656 lines

============================================================================
BBreqdat.exe (c)1992 Freeman M. Crosby W1NPR
============================================================================
   Entire Beginner's BBS Tips Series (c) 1990 1992 by Bill Britton, KB4VOL
============================================================================
Sample format of the text file databases used with BBreqdat.exe

This is an adaption of both BBreqhrc.exe and BBreqhfd.exe which operate on
databases provided by Ham Radio Classified and are also available.

A simple text file is used to create small databases which may be accessed
by the BBreqdat.exe server.

These may be edited by any text editor or the EF command in REBBS.

Use care if a word processor is used and save in ASCII format.

This system is a simple way to combine several files or subjects into one
larger file saving overhead and providing continutity to a series of articles
or data.

You will name each file whatever you wish the user to request such as the
REQTIP example. The server uses a suffix after the command to determine which
database to access during it's run. All files related to each database will
have the same Filename

The size of each database will be determined by the speed of the computer used
and the time available for a sequential access to the last file. Some testing
will soon determine how large each one may be.

The example used is the BBS-TIPS series by KB4VOL and you will see how the
Subjects are set up to determine the sections of the database and also provide
an index or listing of available files.

Each section, file or whatever you wish is separated by a code word Subject:
EXACTLY as stated on the left margin of a separate line.

As users seldom are able to make a proper request we have tried to outsmart
them and only use a portion of their Subject line request to look for the
file they wish. The Database Subject: line may have a nice explaination (keep
it to one line) of the file but you must include a numeric number in it
which will be the only thing the server looks at.

You may use something like Kenwood modification Part 1 or whatever you wish.

Your user reply will indicate the user select his request by number. We hope
they can get one in there somehow !

In the example Subject: BBS-TIPS #3 will be returned to a user who addressed a
message REQTIP @ BBS with any of the following message Subject line requests:

3
Send me file # 3
Hey Jim I need 3
BBS-TIP #3
Tip-3please
Find BBS-TIP #3

Even "Send WB4VOL's tip 3" will work a we only pick the Last numbers they use.
There is limit on the number

Most series are in Part # ?? so you should be able to work a numeral into
the subject they request.

Be sure to have a space after the numerals in the Subject: or have them the
last character on a line.

Subject: BBS-TIP #1 , Introduction to the BBS-TIPS series

Several years ago I send a series of BBS Tips for those just starting out
in packet.  Since then there have been many newcomers to this fascinating
part of our hobby and I've been asked to repeat the series, updated to
include some of the new commands and features now available on many BBS's.
Hang in there, this is really easy and a lot of fun!

When the average ham (if there is such a thing) gets set up for packet, he
usually sits and stares at the screen for a while, watching stuff float by.
One of the things he notices is an occasional beacon from his local BBS.
(BBS means Bulletin Board System.)  Gathering up every ounce of courage he
can muster, he nervously tries connecting to the thing and is shocked when
it answers.  But after the opening greeting, it gives him a list of letter
commands and waits expectantly for him to enter something.  Having no idea
what those commands mean, he disconnects in a panic and wonders what to do
next.

Our friend is not alone.  Many newcomers are confused by the diverse
commands and features found on today's bbs systems.  With our Beginner's
BBS Tips series we'll explore those commands, and try to remove some of
the mystery!

First things first.  When you connect to a BBS it will rapidly go through
it's USER file to see if you've connected before.  If it doesn't find your
call it will assume you're a newcomer and ask you to REGISTER.  This is
simple, and quite painless.  It will probably ask you for your first name.
Type it and press the ENTER (or RETURN) key.  It will then greet you by
name and ask for your zip code.  Next it will ask you for your "home" BBS.
This is the BBS where you would normally check in to get your mail, which
are messages addressed to you.  If you don't have one yet, and would like
to use the one you're connected to, enter it's call.  They'll be glad to
have you!  But remember, you should only have ONE "home" BBS.  If there's
more than one in your area you can REGISTER on as many as you like, but
only indicate ONE BBS CALL as the one you'll check into most often.  Many
newcomers tell every BBS in sight that "they're the one," but this is a
big mistake!  If mail arrives for you, BBS "B" will sit on it without
forwarding it to BBS "A" even though you've only checked into BBS "B" once.
Do that, and you'll wonder where your mail went!  You can always change your
mind later, but if you do be sure to re-REGISTER your new "home" BBS with
the old one.  Another very good idea is to always send (originate) your
messages from your HOME BBS.  That way replies, if any, will always come
back there.

Once you've registered, the BBS will welcome you and return to it's PROMPT
line, which is that string of letters that threw our friend into a panic.
Those commands are really easy, and we'll start looking at them next time.
Questions or comments on this series are welcome.
73...Bill, KB4VOL @ KB4VOL

Subject: BBS-TIP #2 , (L)ist commands explained

This time around let's look at the (L)ist command and the many ways it can
be used on your local BBS.  If you enter L at the prompt you'll get a
listing of all messages, except those tagged (P)ersonal which are addressed
to someone else.  Remember, on most BBS's the L command will ONLY LIST THOSE
RECEIVED SINCE YOU LAST USED IT.  Enter it again and the BBS may report
NOTHING FOUND as nothing new was received since you first entered it a few
moments ago.  This can confuse a lot of people!  However, it's a good
command to use if you check into your BBS daily, as you should.  Do an L
and you'll see "what's new" since you last checked in.  See something
interesting?  Note the message number, and enter R MSGNUMBER at the next
prompt.  R means (R)ead, and we'll cover more on that command later.

Most users prefer the LL xx command. (Note the space!)  As an example, LL 20
gives you the last 20 messages received.  Enter it again, if necessary, and
it'll repeat the list.  Obviously the xx can be any number you choose,
within reason.  Don't do a LL 100 or you'll go bananas.

Now let's talk about using the (L)ist command to pinpoint certain types of
bulletins.  That's where the L@ and the L> commands are helpful.  As an
example, let's say you're interested in AMSAT information.  Some of these
are send to ALL @ AMSAT.  To see those displayed enter L@ AMSAT (note space)
which means LIST AT AMSAT.  But there are others addressed as AMSAT @ ALLUS.
The word AMSAT is in the "TO" space, rather than "AT."  How do we see those?
Simple!  Just enter L> AMSAT which means LIST TO AMSAT.  A few more examples.
Just interested in ARRL messages?  Enter L@ ARL to get them.  How about
those bulletins listing equipment for sale?  These are usually addressed
to either SALE or 4SALE.  Enter L> SALE or L> 4SALE to see them.  Maybe
someone needs something.  Try L> WANTED to see those.  The reverse of
L> is L< which means LIST FROM.  This might be helpful if KD4ZZZ sent out
a bulletin and you want to see it.  Enter L< KD4ZZZ and you've got it.

Several BBS programs have a new feature!  Using it, you can look for a
certain type of bulletin using a wildcard search for a word in the SUBJECT
line.  Let's say you're interested in "For Sale" messages and nothing else.
Try entering LS *SALE* (note space!) to list all that have the word SALE
somewhere in the title.  Another type of BBS will respond to the command
L"SALE" (note NO space.)  Of course you can use this to search for any
subject word you choose.  If your BBS doesn't respond to either command,
drop a note to the SYSOP and ask him if his BBS has this feature.

Personal messages?  Enter LM for yours, which means (L)ist (M)ine.  You
can also use L> (CALLSIGN) or L< (CALLSIGN), but remember you can't
read personal messages unless they're addressed to you, or sent by you.

Formal NTS traffic is important, and you should always see if there's
any you can help deliver.  LT, which means (L)ist (T)raffic, will bring
you a listing of whatever's there.  If you are successful in delivering
a piece of traffic, use KT (MESSAGENUMBER) to kill it off the bbs so no
one else will attempt a duplicate delivery. (KT means (K)ill (T)raffic.)

Next time we'll start talking about the S command, and refer to one
L command you should avoid!  Questions and comments about this series
are welcome.
73...  Bill, KB4VOL @ KB4VOL

Subject: BBS-TIP #3 , More on (L)ist , (S)end

First, as promised, let's look at that L command you should try to avoid.
It's LB which means (L)ist (B)ulletins.  There's nothing wrong with the
command itself, but you may hate what it does.  BBS's receive a mountain of
bulletins every day.  Some let them pile up for quite a while.  Enter LB and
the BBS will proceed to send you a list of every bulletin it has, which
could be hundreds!  This will take forever to transmit, completely tie up
the frequency and, by the time you get to the 100th or so, your brain will
be so numb you'll probably disconnect in self-defense!  Far better to use
the LL xx command, which was covered in BBS TIP #2.  Connect to your BBS
regularly, enter LL 20 or whatever, and you'll see what's new without your
brain or the BBS blowing a fuse!

Now, let's start looking at the S command which is very often misused.
Let's see what we have available.  Most BBS's will recognize SP, SB and ST.
The first letter S means SEND.  That alerts the BBS that a message is
coming, and it prepares to receive it.  The second letter shows the TYPE
of message, P, B or T.  Today, let's begin with SP.

SP means (S)end (P)rivate.  The only person who can read this message is the
station to whom it's addressed.  Examples:
SP KD4ZZZ would be a message sent to a station using the same BBS.
SP KD4XXX @ KD4YYY indicates the station is at another BBS, perhaps at
another LAN or even out of state.  Your HOME BBS will automatically forward
this message for you.  Pretty neat, huh?

Important!  Nowadays BBS's use something called HIER addresses as an aid
in forwarding messages to other BBS's.  These are location "indicators"
which help them route the message in the right direction.  As an example,
mine is KB4VOL.#WPBFL.FL.USA.NA which automatically tells other BBS's that
I'm in the West Palm Beach area, in the state of Florida, etc.  All BBS's
are now equipped with utilities which automatically scan the headers of
all messages looking for HIER addresses that are new, or changed.  This
information is stored in a huge file which covers just about every BBS in
the world, and is constantly being updated.  Although some SYSOPS will
argue this point, it probably isn't a good idea to try to add the HIER
address yourself unless you're sure of it, and very careful to enter it
correctly.  Let the BBS do it!  As soon as it sees a message addressed
to an "@ BBSCALL" (example: SP KD4YYY @ KD4ZZZ) it will look KD4ZZZ up
in it's HIER file, AUTOMATICALLY append the correct address to the call,
and the message is on it's way!  But if you enter the HIER address yourself
and goof (example: SP KD4YYY @ KD4ZZZ.PODUNK.USA) the message will go
nowhere, as the BBS has no path for that wierd address.  Your message will
just sit there until the SYSOP notices it...if he does.  Then he will have
to manually change it, which won't make you one of his favorite people!

Another important thing!  When you enter a message, WATCH THE SCREEN and
press ENTER or RETURN after a word near the end of EACH line!  If you
don't, a word will wind up beginning at the end of one line and finishing
on the next.  This makes your message hard to read and difficult to
transmit.  This may cause dropped or garbled words or sentences, and the
person receiving the message may have no idea what you're talking about!
Of course you may have no idea either, but that's another problem.

Next time we'll cover SB and ST, two other S commands which can confuse
a beginner.  Comments and suggestions on this series are welcome!
73...Bill, KB4VOL @ KB4VOL

Subject: BBS-TIP #4 , SB & ST commands

In our last bulletin we talked about the correct use of the SP command.
Today, let's look at SB and ST.

SB means (S)end (B)ulletin.  This is the form used when you want it
to be read by everyone.  Bulletins are usually sent to an @ DESTINATION.
If you just send it as SB ALL it will just sit on the BBS for local users to
read.  Send it as SB ALL @ DESTINATION and it'll be forwarded.  Examples:

SB ALL @ FLBBS covers BBS's over the entire state.
SB ALL @ ALLUS blankets the nation.

There are many other @ DESTINATIONS, including local and regional ones, but
you get the idea.

Sometimes it helps to use a special address to alert users who might be
interested in a specific subject, so they'll read your bulletin.
SB REBBS @ FLBBS and SB AMSAT @ ALLUS are examples.

Important!  Sometimes users address a bulletin as SP instead of SB.  Big
mistake!  This makes it a PRIVATE message and no one, except BBS sysops,
will be able to read it.  Do this and you'll wonder why you never get any
replies!  Also, don't address ANY message as just S (SOMETHING).  Many BBS's
automatically append a P to an S-only message making it SP.  If you intended
to send out a bulletin, you've had it!  Always start your messages with SP,
SB or ST.

ST means (S)end (T)raffic.  This is used only for formally formatted NTS
messages with a routine number, day/time, group count, etc., along with the
complete address and phone number of the addressee. Also, to aid in routing,
always put the town, state and phone number in the subject line.  Formal
traffic messages may be sent @ the destination BBS, if you know it.  If not,
use ZIP @ NTSxx where xx is the 2 letter state abbreviation.  Example:

ST 33455 @ NTSFL
(SUBJ.): Hobe Sound FL 555-1111

Remember, NEVER use ST for anything but a formally formatted NTS message.

Next time we'll look at the only way to actually talk to a real live SYSOP!
Suggestions or comments on this series are welcome.
73...Bill, KB4VOL @ KB4VOL

Subject: BBS-TIP #5 , Some common errors

What follows could have happened on any BBS anywhere, and probably does.
I've changed a few names and calls to protect the guilty.  First, let's set
the scene.  Norman Newcomer has had his TNC for several days.  Flushed with
success at his ability to have a keyboard qso with a few other users, he
decides to try connecting to a BBS.  Besides, he met the guy who runs the
thing at the club meeting the other night, and wants to say hello.  Here's
what happened, sort-of:

+++ CONNECTED TO KD4ZZZ
KB4VOL BBS >
"Hi Bill, how's it going?"
+++ WHAT?
KB4VOL BBS >
"Bill, this is Norm.  We met at the club meeting the other night."
+++ WHAT?
KB4VOL BBS >
"Hey, don't you remember?  I bought you five beers afterward!"
+++ WHAT?
KB4VOL BBS >
"I was the guy who gave you all those gal's phone numbers..."
+++ WHAT?
KB4VOL BBS >
"...and I was keeping them for myself!"
+++ DISCONNECTED

What happened here?  Well, Norm didn't realize that Bill was probably
nowhere near the hamshack, and HE WAS TALKING TO A COMPUTER!  Now, computers
are wonderful things, but in a BBS they're programmed to respond to certain
commands, and ONLY to those commands.  Throw anything else at it, and it
will respond with *** WHAT? or something similiar.  It's simply telling you
it doesn't recognize what you're sending as a command, and wants you to
try again.  However, after a certain number of these "errors" have been
received, most BBS's will automatically disconnect, which is what happened
in our little scenerio.

So please remember, next time you're connected to a BBS, use the commands
the thing will recognize.  If you decide you want to have a keyboard QSO
with the SYSOP (SYStem OPerator), enter the letter T for (T)alk.  The BBS
will tell you it's paging him and his computer will let go with a series of
squawks that can be heard down the block. If he doesn't respond after about
a minute or so, the BBS will tell you he's not available, or words to that
effect, and invite you to leave him a message with the SP command.  Of
course if he's there, he'll come right back to you.  Simple, huh?

Now, let's start looking at the versatile R command.  R means (R)ead and we
use it to read a message or bulletin. Example: R 2024 would give us message
number 2024 etc.  We can also read a group of them at once:
R 2024 2032  (Note spaces!)
But unless you're a speed-reader, it's probably better to read them one at
a time.  If you request a whole bunch the BBS will send one after the other
in rapid succession.  This will cause a condition known as "crossed eyes,"
and banging on the keyboard won't help.  Just do a L or LL xx command,
note the ones that look interesting, and take your time reading them.

Remember, you can only read bulletins, NTS traffic and mail to or from you.
Most BBS's will not let you read private messages addressed to someone
else.  Chances are, when you use one of the (L)ist commands (covered in BBS
Tip #2) you won't even see any "private" messages, other than your own.

Next time we'll continue looking at the R command, including one that
frustrates a lot of users!  Suggestions or comments on this series are
welcome.
73...Bill, KB4VOL @ KB4VOL

Subject: BBS-Tip #6 , (R)ead

Today we'll continue looking at those versitile R commands.  There's a lot
more than just R MESSAGENUMBER!  Let's say you sent a message to KB4VOL and
you want to reread it, but forgot it's message number.  Enter R> KB4VOL
(note space) and you've got it.  But, suppose he sent out a bulletin and
you've forgotten the number of that one, too.  Enter R< KB4VOL and there it
is.  Don't forget, the symbol < means "from," and the symbol > means "to."
We can use these with (L)ist as well as (R)ead commands.

Taking this command one step further, let's say you want to read a bulletin
addressed to RTTY @ PODUNK but you've forgotten the message number.  You
can enter R> RTTY (Read TO RTTY) and you've got it.  You could also enter
R@ PODUNK (Read AT Podunk) and you'll see it.  But be careful!  If a lot
of bulletins are sent @ PODUNK that command will give you the one you want,
along with all the rest of them!  It might be better to use the (L)ist
command (covered earlier) to spot the one you want, then use R to read it.
Otherwise you might get a long string of messages from the BBS, while the
frequency gets tied up and your brain turns to mush.

Now let's look at the one R command that frustrates a lot of users!  It's
RM which means (R)ead (M)ine.  Say you check into your home BBS and after
the usual opening it announces it has a message (mail) for you.  "Hey, this
is neat!" you say. You don't bother getting the message number with LM
(List Mine), and you grab the easy way.  You enter RM and a message from
Aunt Tillie floats by on the screen.  Then you read a couple of new
bulletins and decide you want to read Aunt Tillie's again.  You enter RM
a second time and the BBS says NOTHING FOUND, or words to that effect.
What happened?  Did the BBS eat it?  Nope!  What it's telling you is nothing
NEW has been received since your previous message.  You already saw that,
so it's been tagged as having been read.  Beating on the computer won't
help, and you'll just break something.  Use LM to see it listed, then
R MESSAGENUMBER to read it again.  Incidently, when you're done reading
your messages, it's a courtesy to kill them with the KM (Kill Mine) command.
Your friendly neighborhood SYSOP will thank you for that.

Next time we'll take a look at a few R commands that are considered a
"no-no," but they're on most BBS's and you should know how to use them
correctly, without incurring the wrath of everybody in sight!
Comments and suggestions on this series are welcome.
73... Bill, KB4VOL @ KB4VOL

Subject: BBS Tip #7 , More on (R)ead

Today we'll continue our look at the R command which, as we now know,
means (R)ead.  R 1234 would bring us message #1234.  RM can be used
to Read Mine, etc.  Very nice so far, but a few R commands are a no-no!
Some of these may not be available on your local BBS, but you should know
to avoid them if they are.

In an earlier bulletin we discussed the LB (L)ist (B)ulletins command
which you should try to avoid, as it could bring you a flood from the
BBS, tie everything up, and cause everyone on frequency to hate you.
Well, the same applies to a sneaky little command called RA or RB, which
works on some of the BBS programs.  Nice little command, but please don't
use it!  You're asking the BBS to let you read EVERY bulletin it has, which
could be hundreds!  If you thought LB brought on the wrath of the local hams,
wait til you see what this one does.  They're liable to make a midnight trip
to your home and stick pins in your coax!

Another problem could be caused by the the RD command which is available on
many BBS's.  There's nothing wrong with the command, BUT BE CAREFUL HOW YOU
USE IT!  RD > YYMMDD will give you all messages NEWER than that date.  So,
if you've been away for a couple of days, and today's May 10th, you could
enter RD > 920508 which would give you all the messages posted for the past
48 hours, etc.  That's OK, but let common sense prevail and don't tie
everything up.  Obviously asking for a month's worth is pure dumb.  You'll
never be able to read them, nor would you be interested in all of them.
Use the LL xx command (covered earlier) and pick out those you want to read.

Now, before I get a flood of angry notes from sysops for even MENTIONING
these "forbidden" commands, let me remind you that they ARE listed in
the "(H)elp R" files of bbs's so-equipped, so anyone could stumble across
them.  Perhaps some day those who write the software will make these
"sysop-only," but in the meantime we must rely on the integrity of users
NOT to use them for fear of fast and terrible retribution!

Another R command that isn't used too often can be helpful in tracing
the path of a message.  Instead of using R 1234, use RH 1234.  RH means
(R)ead (H)eader, and it will show you the bbs's and locations your
message took in reaching you as well as the dates and times it was received
at each bbs.  If a message from Aunt Minnie took a week to reach you, you
can see where it was held up and drop that sysop a nasty note.  He'll
just love hearing from you.

Again, remember some of these commands are not available on all BBS's.
If you enter one, and it burps and says *** WHAT? then use something else.

Next time we'll begin to look at the W and D commands, which give you
access to the world of information stored in a BBS's files.  Questions
and comments on this series are welcome.  Just don't stick pins in
my coax!
73...Bill, KB4VOL @ KB4VOL

Subject: BBS-TIP #8 , (W)hat

Today let's see how we download files from our local BBS.  This seems to
confuse a lot of people, so we'll take it slow and easy.

First of all you might ask, "Why should I want to download files?  I see
everything that's new when I connect to the bbs every day."  True, you'll
see the latest bulletins, but what of the other stuff that may be available?
Often a BBS sysop will collect and store a lot of valuable info in files
that can be downloaded by users just like you.  A lot of it can be very
interesting and helpful.  Why read just one book, when you have a whole
library at your fingertips?

Okay, but how do we find out what's in the library?  Ask the librarian!
On a BBS her name is W which means (W)hat.  Enter W at the prompt, and
the bbs will give you a list of DIRECTORY TOPICS.  These are the different
subjects covered in different sections of our BBS "library."  As an
example, entering W might give us a list like this:
GENERAL      -- General information
NEW          -- Info and tips for packet beginners
LISTS        -- NODES, PBBS and CLUB lists
FREQ         -- Scanner and SWL frequencies
MODS         -- Tips on modifying equipment
(etc.)  Now before you get too excited, let me stress that every BBS will
probably have a different list, depending on what the SYSOP believes will be
of interest in his area.  These are just a few of the file directories
available at the KB4VOL BBS, but each BBS will be different.  Some will have
more...some less, and some may just have a list of the directories, without
any description.

"Wonderful," you say, "but how do I get at them?"  Well, first things
first!  Now that we know what topics (directories) are in our BBS library,
we have to find out what "books" are available under each topic.  That's the
second of our W commands.  This really isn't as hard as it may seem, so hang
in there!

Each directory contains a bunch of individual files.  To see what they are
we enter:  W DIRECTORYNAME   Example:  Our initial W command gave us the
complete list, and maybe one was called MODS.  We want to see what's in
there, as there may be some info about our two-tube "Super Whatzis."  So, we
enter W MODS and the whole list will be presented for our scrutiny.  If our
pride and joy is listed we might find something interesting about it, like
how to make it work.

Now before you start banging your head against a wall, let me mention that
some BBS's handle their file listings a bit differently!  If you enter W
for the list of directories, it might come back with this:
WA  MODS
WB  ARRL
WC  AMSAT
(etc.)  This is a bit different from what we had before, but the only real
difference is listing the file-types under each directory.  Example:  If we
see this type of listing, and we want to see the MODS list, enter: WA -not-
W MODS and you'll get it.  For ARRL enter WB and so on.  Simple, huh?

Now that we know how to browse through our BBS "library," we'll see what
we have to do to get at these files.  That's handled by the D command, and
we'll look at that in the next bulletin.  Questions or comments on this
series are welcome.
73...Bill, KB4VOL @ KB4VOL

Subject: BBS-TIP #9 , (D)ownload

Well, we've covered the different ways of using the W command to see the
files in the subdirectories of the bbs "library."  Now let's see how we can
get at them.  For this we use the D command which means (D)ownload.  But
there are several ways of using it, depending on the BBS program being used!

Okay!  We mentioned one where the W command might bring this:
ARRL
MODS
(etc.) With this type of bbs we see what's in each directory TOPIC by
entering W TOPIC with W MODS as an example.  Let's say we have a WHIZBANG
rig, and we want to see if there are modifications for it.  Part of the
W MODS list might show:
WHIZBANG.1
WHIZBANG.2
Wow, there are two of 'em!  But how do you get at them?  With this type
of BBS enter:  D MODS WHIZBANG.1  (note spaces) and you'll get it.  After
you've got that one safely tucked away on your printer or disk drive you can
download the other one with D MODS WHIZBANG.2

Something to remember!  Most BBS's will show the file size.  Example:
DINGBAT.DOC  13k
But most sysops will take a large file and break it down into smaller pieces
before putting it into their subdirectories.  So it's quite possible that
our WHIZBANG.1 and WHIZBANG.2 aren't too separate MODS, but a long one
broken into two parts for ease in downloading.

If, when you enter the command W for (W)hat, you get a list like this:
WA  ARRL
WB  MODS
(etc.) you're connected to another kind of BBS!  Here we see what files are
in each category by entering WA, WB etc.  Let's see what's in the MODS file
by entering WB.  After we get the list we see there's a file for our
WHIZBANG rig, and it's called WHIZBANG.INF but how do we get it?  Simple!
Enter DB WHIZBANG.INF and there it is!  (Note space after DB.)  What we've
done is to request the BBS to (D)ownload that file from subdirectory B.
Hey, this is easy!

Here are some more.  If, when you enter W, you get this:
BANDPLAN.TXT    2045
MODS            <Dir>
(etc.) then you're looking at one combining direct-access files with those
in subdirectories.  To (D)ownload the direct ones enter: D BANDPLAN.TXT
as an example.  To see what's in the subdirectories, enter: W (DIRECTORYNAME)
or W MODS.  Now downloading from a subdirectory on this type of BBS is a bit
different!  We must use a slash mark in the command. Here's an example:
D MODS/WHIZBANG.INF
Note: many sysops using this software don't bother with subdirectories.
In that case you'll see the whole list when you enter W with no <Dir>
entries at all.  Just use D FILENAME.EXT to get what you want.

Next time we'll show you how to tell if Joe down the street has been using
the BBS, and also cover "What-to-do-when-all-else-fails!"  (Screaming at
your computer is NOT the answer!)  Questions or comments on this series are
welcome!
73...Bill, KB4VOL @ KB4VOL

Subject: BBS-Tip #10 , Operation

Okay, let's set the scene.  You want to get hold of Joe, KD4ZZZ, who's a ham
over in Podunk.  You know he was active in packet, but you haven't seen him
on lately.  What to do?  Well, the obvious thing would be to leave him a
message on your local BBS with the SP command.  But, it might just sit there
if he doesn't connect, or see it in the BBS's "Mail" beacon.  But you have
another choice.  You can play detective!

Some BBS's accept the DU command, which means (D)ownload (U)ser.  To use it
enter:  DU (CALLSIGN).  As an example, DU KD4ZZZ.  Now if Joe has registered
at your local BBS it might come back with a line like this:

KD4ZZZ  920215/1410  6  KD4YYY  JOE

(There might be other information given, but this is what we're interested
in.)  Hmmm!  According to this, Joe has only checked into that BBS 6 times,
and the last time was back on February 15 at 1410.  Gee, guess he's not on
packet anymore.  But wait, here's another clue!  He listed KD4YYY as his
"home" BBS, and that one is in the next county on a different frequency!
On a hunch we connect to it, do a DU KD4ZZZ and there he is, still very
active!  Now we know we can send him a message simply by entering
SP KD4ZZZ @ KD4YYY on our local BBS, and it will automatically forward
it to his BBS.  Hey, our detective work has paid off!

But the DU command only works on some BBS programs.  If yours is running
something else, and you enter DU (CALLSIGN) it might come back with an error
message indicating it doesn't understand what we want.  Now what?  Well, we
can try the J command which lets us look at the BBS's log.  It won't be as
informative as the DU command, but it might give us a clue.

Unfortunately, the way to use the J command also depends on what kind of
program your BBS is running!  One of these days those who write the BBS
software will standardize the commands, but it hasn't happened yet.  This
leads to a high FL (Frustration Level) among users.  Anyway, try J by itself
and see what you get.  If the BBS is running separate ports on different
frequencies, enter JA, JB (etc.) to get the list of calls.  But these will
probably be calls HEARD lately, not necessarily those who CONNECTED.  To get
those, try J, JL or JK.  If it's a multi-user program, like the AA4RE BBS,
JN will show you who's connected at the moment, besides yourself.  Don't
be afraid to try different commands on a BBS.  You can't "hurt" it!  If
it doesn't recognize what you sent as a valid command it will give you
an "error" message, and you can try something else.  Remember, you can
always enter H or ? to get a list of the commands it DOES recognize!  In
essence you're saying, "Okay, stupid, if you don't like what I'm sending,
tell me what WILL make you happy!"  The H or ? will usually produce a little
list of the commands the thing will accept, and you can go from there.

Well, almost time to wrap it up.  The next bulletin will be the last of
our Beginner's BBS Tips.  In it we'll talk about "What-to-do-when-all-else-
fails."  Questions or comments on this series are welcome.
73...Bill, KB4VOL @ KB4VOL

Subject: BBS-Tip #11 , (H)elp

Are you getting frustrated because every time you enter something the BBS
responds with "What?" "Huh?" or, worse yet, "Go away!"  (No, I've never seen
one do that, but it's an interesting thought!)  Anyway, you've tried every
command you can think of, and the dumb thing still doesn't understand you.
Screaming will only startle the neighbors, so don't do that.  Instead, let's
see "What-to-do-when-all-else-fails?"  The answer is simple...ask for help!

However, this brings us to the old problem.  Different BBS programs
recognize slightly different commands, but the (H)elp command is pretty
standard.  So, enter H by itself and see what you get.  It should be a short
list of the commands available on that BBS, and what each one does.  Okay,
let's say you want to find out how to (S)end a message.  We now know that H
means (H)elp, so first try H (COMMAND) or in this case H S (note the space!)
If your BBS responds to this command it should give you complete directions
on (S)ending a message.  But suppose you get that dreaded "What?" again?
Okay, some do it a slightly different way.  Try entering ?(COMMAND) or ?S
in our example (note NO space!)  Either one should work.  But, if all else
fails, or you don't understand the directions the BBS gave, what then?
Ask the bbs sysop (SYStem OPerator)!  Try the T command, in case he's in the
shack, or leave him a message with the SP command, both of which were
covered in earlier Tips bulletins.  Remember, your sysop WANTS to help you
get the best use out of his BBS!  He probably has several thousand dollars
tied up in computers, rigs and associated equipment, plus untold hours spent
every day just maintaining the files and messages for the benefit of the
local packet community.  He wouldn't have made this committment if he wasn't
more than willing to help packet newcomers learn and and enjoy this
fascinating part of our hobby.  So, don't ever hesitate to ask him about
anything.  Remember, there is no such thing as a "dumb question!"

Well, we've come to the end of the line with our Beginner's BBS Tips series,
and I hope they've been helpful to those just starting out in packet.  We've
tried to cover most of the basic commands you'll need to use the BBS your
local sysop has provided.  Check in often, read the bulletins that interest
you, download the files available, and use it to send or receive messages
from your friends.  That's what it's there for.  Enjoy it!
73... Bill, KB4VOL @ KB4VOL
  **************************************************************************
   Entire Beginner's BBS Tips Series (c) 1990 1992 by Bill Britton, KB4VOL
    Reproduction and distribution within the amateur community is granted.
      If all or part of this series in used in club newsletters, I would
            appreciate a copy.  My address is good in the Callbook.
  **************************************************************************